Skip to content

[TRTLLM-15177][chore] Kimi K3 post-merge cleanup: config/import/test hygiene + L0 wiring - #17413

Merged
brnguyen2 merged 13 commits into
NVIDIA:mainfrom
brnguyen2:k3/15177-cleanup
Aug 10, 2026
Merged

[TRTLLM-15177][chore] Kimi K3 post-merge cleanup: config/import/test hygiene + L0 wiring#17413
brnguyen2 merged 13 commits into
NVIDIA:mainfrom
brnguyen2:k3/15177-cleanup

Conversation

@brnguyen2

@brnguyen2 brnguyen2 commented Aug 7, 2026

Copy link
Copy Markdown
Collaborator

Summary

Post-merge cleanup follow-ups deferred from #17269 (Kimi K3 / KimiLinear model), tracked in TRTLLM-15177. Low-risk, K3-scoped hygiene.

Included

  • config: KimiLinearConfig.keys_to_ignore_at_inference list to tuple (immutable class-level default).
  • modeling_kimi_linear.py: hoist gc/json/ExitStack/safetensors.safe_open to module level (removed 3 redundant local import gc), drop the json->_json alias, move the latent_moe_use_norm assert to the top of KimiK3MoERuntime.__init__.
  • modeling_kimi_linear.py refactors (behavior-neutral, code moved verbatim):
    • split the ~450-line KimiLinearForCausalLM.load_weights into focused methods (_validate_checkpoint_keys, _load_trunk_params, _load_expert_slices, _finalize_weight_load) behind a short orchestrator;
    • extract the duplicated FP8 weight-read module swap (nested _swap closures in the MoE-MLP and MLA converters plus the inline KDA o_proj conversion) into a module-level _swap_linear_to_fp8_weight_read helper.
  • Move the test-only reference MoE block (KimiK3SparseMoeBlock + _moe_kernels/_mxfp4 helpers, used only by test_kimi_k3_situ_moe.py) out of the runtime package to tests/unittest/_torch/modules/moe/kimi_k3_ref_moe/, rewriting relative imports to absolute. The runtime package keeps the gate and shared MLP/RMSNorm pieces modeling_kimi_linear.py uses.
  • KDA fused-verify parity test: real KimiLinearConfig instead of SimpleNamespace, @torch.no_grad() decorators, module-level imports, drop the __main__ block, ruff-format.
  • L0: wire 6 K3 unit suites into l0_b200.yml; the 7th (test_kda_prefill_op.py) is deliberately excluded pending the B200 prefill-op NaN (TRTLLM-15204).

Deferred (still tracked in TRTLLM-15177)

  • Folding kimi_k3_mla into modeling_kimi_linear.py: small on this base (one ~260-line module with a single importer, already built on the general MLA class), but kimi_k3_mla_attention.py has diverged on the K3 feature branch (decode-backend selection changes not yet in main), so deleting the module here would turn the next branch sync into modify/delete conflicts. Deferred until the branches converge.
  • Migrating kimi_k3_moe into modeling_kimi_linear.py: [None][perf] Shard Kimi K3 MLPs with tensor parallelism #17312 simplifies the MoE package (standard GatedMLP for the shared experts and first dense layer) and is the right base for this migration; it targets the K3 feature branch and is not in main yet. Deferred until [None][perf] Shard Kimi K3 MLPs with tensor parallelism #17312 reaches main.
  • Overlap note: the reference-MoE relocation in this PR and [None][perf] Shard Kimi K3 MLPs with tensor parallelism #17312 move the same test-only code into the unit-test tree under different names (kimi_k3_ref_moe/ package here vs flat *_test_utils.py modules there). The PRs target different branches (main vs feat/kimi_k3), so neither blocks the other; the branch-sync merge after both land should keep [None][perf] Shard Kimi K3 MLPs with tensor parallelism #17312's placement and drop the duplicate.
  • Removing the communication_method plumbing was intentionally dropped. It is not dead: test_kimi_k3_situ_moe.py passes communication_method="ALLGATHER", and communication_factory.py uses it as the default when TRTLLM_FORCE_COMM_METHOD is unset.

Validation

Validated on a Blackwell node (GB300, SM103 — representative of B200; not run on B200 hardware itself):

  • All 6 K3 unit suites wired into l0_b200.yml pass, including the changed test_kimi_kda_fused_verify_parity.py. The excluded test_kda_prefill_op.py fails deterministically on B200 (NaN in every compute-running case, TRTLLM-15204); the full set of 7 passed on GB300 out-of-CI.
  • Test collection (pytest --collect-only) of all 7 suites (6 wired + 1 excluded) is clean, confirming the module-level modeling_kimi_linear import is safe at collection time; imports of the relocated reference MoE module verified.
  • Weight-load refactor checked against a real checkpoint: a layer-truncated Kimi K3 TP4 load + generation was run on the pre-refactor and post-refactor trees; generated token ids match exactly and per-token logprobs are bit-identical across the two runs.
  • pre-commit clean on all changed files.

Related: TRTLLM-15177

Dev Engineer Review

  • Changed KimiLinearConfig.keys_to_ignore_at_inference to an immutable tuple.
  • Refactored Kimi K3 checkpoint loading and FP8 conversion.
  • Added validation, typed helpers, streamed expert loading, page eviction, and expert-slot completeness checks.
  • Changed latent-MoE validation from assert to ValueError.
  • Moved the HF-parity reference MoE implementation to the test package.
  • Removed test-only MoE symbols from runtime exports.
  • Deferred kimi_k3_mla and kimi_k3_moe consolidation.
  • Kept communication_method plumbing unchanged.
  • TP4 checkpoint generation produced identical token IDs and per-token logprobs before and after the refactor.

QA Engineer Review

  • Modified tests/integration/test_lists/test-db/l0_b200.yml.
  • Added these L0 entries:
    • test_kimi_kda_fused_verify_parity.py
    • test_kimi_kda_verify_parity.py
    • test_kda_cache_soundness.py
    • test_kda_prefill_state_parity.py
    • test_attn_res_op.py
    • test_kimi_k3_situ_moe.py
  • Excluded test_kda_prefill_op.py because its compute cases produce NaNs on B200. The exclusion references TRTLLM-15204.
  • Updated test_fused_vs_sequential_two_rounds.
  • Updated Kimi K3 SiTU MoE tests, including fused/reference parity, mutation, error handling, mapping, split selection, and TP-shard loader tests.
  • The modified test files are covered by test-db/l0_b200.yml.
  • Test collection and pre-commit checks passed.
  • Two CI runs failed. A later fail-fast-disabled run passed after automatic retries.
  • Validation was performed on GB300.
  • Verdict: sufficient.

@brnguyen2
brnguyen2 marked this pull request as ready for review August 7, 2026 10:19
@brnguyen2
brnguyen2 requested a review from a team as a code owner August 7, 2026 10:19
@brnguyen2

Copy link
Copy Markdown
Collaborator Author

/bot run

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #64579 [ run ] triggered by Bot. Commit: 2915fee Link to invocation

@coderabbitai

coderabbitai Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

Walkthrough

Kimi K3 runtime loading now supports shared FP8 conversion and staged expert loading. The test-only reference package adds MXFP4 and native SiTU MoE paths. KDA parity tests, MoE tests, and Blackwell pre-merge coverage use the updated modules.

Changes

Kimi K3 runtime and reference validation

Layer / File(s) Summary
FP8 conversion and runtime contracts
tensorrt_llm/_torch/configs/kimi_linear.py, tensorrt_llm/_torch/models/modeling_kimi_linear.py
Kimi K3 projections use shared FP8 conversion. BF16 storage is released after conversion. Latent-MoE configuration uses explicit validation.
Staged checkpoint loading
tensorrt_llm/_torch/models/modeling_kimi_linear.py
Checkpoint loading validates keys, separates trunk and expert loading, streams expert shards, validates expert slots, and finalizes KDA decoding and FP8 conversion.
Reference MXFP4 and SiTU MoE path
tests/unittest/_torch/modules/moe/kimi_k3_ref_moe/*, tensorrt_llm/_torch/modules/kimi_k3_moe/__init__.py
The test-only package adds MXFP4 utilities, expert-weight packing, SiTU parameters, and native TRTLLM-Gen invocation. Runtime exports no longer expose the reference MoE components.
Parity tests and pre-merge coverage
tests/unittest/_torch/modeling/test_kimi_kda_fused_verify_parity.py, tests/unittest/_torch/modules/moe/test_kimi_k3_situ_moe.py, tests/integration/test_lists/test-db/l0_b200.yml
Tests use validated Kimi configuration and reference-package imports. Kimi K3 targets are added to the Blackwell PyTorch pre-merge list.

Estimated code review effort: 4 (Complex) | ~60 minutes

Sequence Diagram(s)

sequenceDiagram
  participant load_weights
  participant _load_trunk_params
  participant _load_expert_slices
  participant _finalize_weight_load
  load_weights->>_load_trunk_params: load trunk parameters
  load_weights->>_load_expert_slices: load expert slices by shard
  _load_expert_slices-->>load_weights: validate expert slots
  load_weights->>_finalize_weight_load: finalize KDA and FP8 state
Loading
sequenceDiagram
  participant ReferenceMoE
  participant invoke_native_situ_moe
  participant TRTLLMGen
  ReferenceMoE->>invoke_native_situ_moe: pass routing and packed weights
  invoke_native_situ_moe->>TRTLLMGen: quantize activations and invoke fused MoE
  TRTLLMGen-->>invoke_native_situ_moe: return BF16 output
  invoke_native_situ_moe-->>ReferenceMoE: trim padded dimensions
Loading

Possibly related PRs

Suggested labels: ci: full pre-merge approved, api-compatible

Suggested reviewers: barry-delaney, qijune, schetlur-nv

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 66.67% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Title check ✅ Passed The title clearly identifies the Kimi K3 cleanup scope, change type, tracking ticket, and L0 wiring.
Description check ✅ Passed The description explains the changes, deferred work, test coverage, validation results, and known CI limitations.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🧹 Nitpick comments (2)
tests/unittest/_torch/modules/moe/kimi_k3_ref_moe/kimi_k3_moe_block.py (1)

51-61: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Prefer relative imports for modules in the same package.

_moe_kernels and _mxfp4 are siblings of this module. The absolute form _torch.modules.moe.kimi_k3_ref_moe.* depends on tests/unittest being on sys.path. A relative import removes that dependency and keeps the package self-contained. The module identity stays the same for the monkeypatch in test_kimi_k3_situ_moe.py, because that test imports the package through the same absolute root.

♻️ Proposed change to relative imports
-from _torch.modules.moe.kimi_k3_ref_moe._moe_kernels import (
+from ._moe_kernels import (
     assert_native_situ_supported,
     invoke_native_situ_moe,
     make_situ_alpha_beta,
     pack_routed_expert_weights,
 )
-from _torch.modules.moe.kimi_k3_ref_moe._mxfp4 import (
+from ._mxfp4 import (
     DEFAULT_GROUP_SIZE,
     dequantize_last_dim_mxfp4,
     quantize_last_dim_mxfp4,
 )
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@tests/unittest/_torch/modules/moe/kimi_k3_ref_moe/kimi_k3_moe_block.py`
around lines 51 - 61, Change the imports of _moe_kernels and _mxfp4 in the
kimi_k3_moe_block module to package-relative imports, while preserving the
imported symbols and module identity used by test_kimi_k3_situ_moe.py.
tests/integration/test_lists/test-db/l0_b200.yml (1)

93-100: 🚀 Performance & Scalability | 🔵 Trivial

Confirm the tier and the pre-merge time budget for the seven added suites.

The entries are module-level, so every test in each module runs. test_kimi_k3_situ_moe.py packs MXFP4 expert banks and launches fused TRTLLM-Gen kernels, and the KDA parity suites run two-round fused-versus-sequential comparisons. If these entries land in the pre-merge tier, they add to the time of every PR on B200. Confirm the intended tier and measure the added wall-clock time.
[operational]

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@tests/integration/test_lists/test-db/l0_b200.yml` around lines 93 - 100,
Confirm the intended tier for all seven Kimi K3/KDA suites in the test list,
keeping them out of pre-merge if their full module-level execution exceeds the
B200 budget. Measure and record their aggregate wall-clock impact, including
test_kimi_k3_situ_moe.py and the two-round parity suites, then update the list
or tier configuration accordingly.

Source: Path instructions

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@tensorrt_llm/_torch/models/modeling_kimi_linear.py`:
- Around line 2188-2191: Annotate every staged-loading helper in
tensorrt_llm/_torch/models/modeling_kimi_linear.py:2188-2191, including
_validate_checkpoint_keys, with parameterized built-in collection types for
weights and expected_keys and explicit return types; annotate weights, params,
and the checkpoint name map at 2218-2234; annotate weights and expert_jobs at
2443-2449; and preserve the explicit return type while using typed call-site
values at 2568-2571. Avoid unnecessary Any and use precise checkpoint,
parameter-map, and expert-job types throughout.
- Around line 663-665: Replace the assertion guarding cfg.latent_moe_use_norm in
the Kimi K3 runtime configuration path with an explicit ValueError when the
setting is disabled or absent, preserving the existing error message and
ensuring the check remains active under python -O.

In `@tests/unittest/_torch/modeling/test_kimi_kda_fused_verify_parity.py`:
- Around line 41-42: Move the KimiLinearConfig and KimiKDARuntime imports below
the dependency guard and its _HAVE_DEPS evaluation so missing CUDA bindings
allow the test module to skip during collection. Keep both imports within the
guarded section used by test_fused_vs_sequential_two_rounds.

---

Nitpick comments:
In `@tests/integration/test_lists/test-db/l0_b200.yml`:
- Around line 93-100: Confirm the intended tier for all seven Kimi K3/KDA suites
in the test list, keeping them out of pre-merge if their full module-level
execution exceeds the B200 budget. Measure and record their aggregate wall-clock
impact, including test_kimi_k3_situ_moe.py and the two-round parity suites, then
update the list or tier configuration accordingly.

In `@tests/unittest/_torch/modules/moe/kimi_k3_ref_moe/kimi_k3_moe_block.py`:
- Around line 51-61: Change the imports of _moe_kernels and _mxfp4 in the
kimi_k3_moe_block module to package-relative imports, while preserving the
imported symbols and module identity used by test_kimi_k3_situ_moe.py.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 43bd6b3b-65a2-4a0a-b39b-101927d2fd8f

📥 Commits

Reviewing files that changed from the base of the PR and between 3cadcf0 and 2915fee.

📒 Files selected for processing (9)
  • tensorrt_llm/_torch/configs/kimi_linear.py
  • tensorrt_llm/_torch/models/modeling_kimi_linear.py
  • tensorrt_llm/_torch/modules/kimi_k3_moe/__init__.py
  • tests/integration/test_lists/test-db/l0_b200.yml
  • tests/unittest/_torch/modeling/test_kimi_kda_fused_verify_parity.py
  • tests/unittest/_torch/modules/moe/kimi_k3_ref_moe/_moe_kernels.py
  • tests/unittest/_torch/modules/moe/kimi_k3_ref_moe/_mxfp4.py
  • tests/unittest/_torch/modules/moe/kimi_k3_ref_moe/kimi_k3_moe_block.py
  • tests/unittest/_torch/modules/moe/test_kimi_k3_situ_moe.py

Comment thread tensorrt_llm/_torch/models/modeling_kimi_linear.py Outdated
Comment thread tensorrt_llm/_torch/models/modeling_kimi_linear.py Outdated
Comment thread tests/unittest/_torch/modeling/test_kimi_kda_fused_verify_parity.py Outdated
@brnguyen2

Copy link
Copy Markdown
Collaborator Author

Reconciliation note on the reviewer suggestions to fold kimi_k3_mla / kimi_k3_moe into modeling_kimi_linear.py, and on #17312:

No code changes from this reconciliation; the PR content and validation are unchanged.

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #64579 [ run ] completed with state FAILURE. Commit: 2915fee
/LLM/main/L0_MergeRequest_PR pipeline #52442 completed with status: 'FAILURE'

CI Report

⚠️ Action Required:

  • Please check the failed tests and fix your PR
  • If you cannot view the failures, ask the CI triggerer to share details
  • Once fixed, request an NVIDIA team member to trigger CI again

CI Agent Failure Analysis

Link to invocation

@brnguyen2

Copy link
Copy Markdown
Collaborator Author

/bot run

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #64604 [ run ] triggered by Bot. Commit: 70e8ee1 Link to invocation

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #64604 [ run ] completed with state SUCCESS. Commit: 70e8ee1
/LLM/main/L0_MergeRequest_PR pipeline #52465 completed with status: 'FAILURE'

CI Report

⚠️ Action Required:

  • Please check the failed tests and fix your PR
  • If you cannot view the failures, ask the CI triggerer to share details
  • Once fixed, request an NVIDIA team member to trigger CI again

CI Agent Failure Analysis

Link to invocation

@brnguyen2

Copy link
Copy Markdown
Collaborator Author

/bot run --disable-fail-fast

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #64686 [ run ] triggered by Bot. Commit: 6de5f5b Link to invocation

… B200 NaN investigation

The suite's compute cases fail the cosine check with NaN on B200 in
pre-merge CI while passing on GB300; keep it out of the B200 list until
the machine-specific numeric issue is understood. The suite remains
wired and green in the GB300 list.

Signed-off-by: Brian Nguyen <brnguyen@nvidia.com>
…200 note

Signed-off-by: Brian Nguyen <brnguyen@nvidia.com>
@brnguyen2

Copy link
Copy Markdown
Collaborator Author

/bot run

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #64943 [ run ] triggered by Bot. Commit: a8f650d Link to invocation

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #64943 [ run ] completed with state SUCCESS. Commit: a8f650d
/LLM/main/L0_MergeRequest_PR pipeline #52778 completed with status: 'FAILURE'

CI Report

⚠️ Action Required:

  • Please check the failed tests and fix your PR
  • If you cannot view the failures, ask the CI triggerer to share details
  • Once fixed, request an NVIDIA team member to trigger CI again

CI Agent Failure Analysis

Link to invocation

@brnguyen2

Copy link
Copy Markdown
Collaborator Author

/bot run

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #64971 [ run ] triggered by Bot. Commit: a8f650d Link to invocation

@zhaoyangwang-nvidia zhaoyangwang-nvidia left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve with nits.

Comment thread tensorrt_llm/_torch/configs/kimi_linear.py Outdated
Comment thread tensorrt_llm/_torch/models/modeling_kimi_linear.py
Comment thread tests/integration/test_lists/test-db/l0_b200.yml
@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #64971 [ run ] completed with state FAILURE. Commit: a8f650d
/LLM/main/L0_MergeRequest_PR pipeline #52805 completed with status: 'FAILURE'

CI Report

⚠️ Action Required:

  • Please check the failed tests and fix your PR
  • If you cannot view the failures, ask the CI triggerer to share details
  • Once fixed, request an NVIDIA team member to trigger CI again

CI Agent Failure Analysis

Link to invocation

Signed-off-by: Brian Nguyen <brnguyen@nvidia.com>

@BowenFu BowenFu left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verified the current head preserves the staged loader ordering and FP8 swap semantics; the latest commit only restores the established list-typed config default. The open bool-to-int and PR-description count threads are non-blocking nits with no runtime or test-coverage impact.

@brnguyen2

Copy link
Copy Markdown
Collaborator Author

/bot run

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #65007 [ run ] triggered by Bot. Commit: fcc4a8b Link to invocation

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #65007 [ run ] completed with state SUCCESS. Commit: fcc4a8b
/LLM/main/L0_MergeRequest_PR pipeline #52818 completed with status: 'FAILURE'

CI Report

⚠️ Action Required:

  • Please check the failed tests and fix your PR
  • If you cannot view the failures, ask the CI triggerer to share details
  • Once fixed, request an NVIDIA team member to trigger CI again

CI Agent Failure Analysis

Link to invocation

@brnguyen2

Copy link
Copy Markdown
Collaborator Author

/bot run

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #65065 [ run ] triggered by Bot. Commit: fcc4a8b Link to invocation

Comment thread tensorrt_llm/_torch/models/modeling_kimi_linear.py
Comment thread tensorrt_llm/_torch/models/modeling_kimi_linear.py Outdated
Comment thread tensorrt_llm/_torch/models/modeling_kimi_linear.py Outdated
@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #65065 [ run ] completed with state SUCCESS. Commit: fcc4a8b
/LLM/main/L0_MergeRequest_PR pipeline #52870 completed with status: 'SUCCESS'

CI Report

Link to invocation

Signed-off-by: Brian Nguyen <brnguyen@nvidia.com>

@juney-nvidia juney-nvidia left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve from qa-function perspective.

@brnguyen2
brnguyen2 enabled auto-merge (squash) August 10, 2026 22:59
@brnguyen2

Copy link
Copy Markdown
Collaborator Author

/bot reuse-pipeline

Review nit: the conversion counter accumulated the helper's bool return
via implicit promotion. Return 0/1 so the accumulator's type is obvious
at all call sites.

Signed-off-by: Brian Nguyen <brnguyen@nvidia.com>
@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #65141 [ reuse-pipeline ] triggered by Bot. Commit: d97a73b Link to invocation

@tensorrt-cicd

Copy link
Copy Markdown
Collaborator

PR_Github #65141 [ reuse-pipeline ] completed with state SUCCESS. Commit: d97a73b
Reusing PR_Github #65065 for commit d97a73b

Link to invocation

@brnguyen2
brnguyen2 merged commit f949d3b into NVIDIA:main Aug 10, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants